| How to use the matrix:
Find the repeater column and then scan down to see
which talkgroups are listed. Or to find where
a talkgroup may appear, locate the talkgroup of
interest and scan across for repeaters that carry
that talkgroup. The entry at the intersection
tells you if it is carried full-time (F) or if it is
on PTT (P). If a "P" then the numbers indicate how
long the talkgroup is active after any local
kerchunk or key-up is initiated. The number
after the forward slash (/) indicates how long it
will hold off most other talkgroups on that timeslot
after the last local kerchunk. These timers
and MCT's help to insure
that an active local talker will not lose that
talkgroup. |
All PTT actions connect
a TG immediately if their is no active talker.
HOWEVER: if there is an active talker, at the
time of your PTT or Kerchunk, the talkgroup traffic will not be
connected or heard by you until the current talker unkeys
and the next talker keys-up. |
Master Control Talkgroups or MCT's and HO's (hold-offs) may be implemented to provide more
control over the timeslot than the timer based "hold
off's". New managers are now being programmed
for active local repeater users MCT control and relying on
Hold-off timers far less but some HO's may be coded as a convenience to users, possibly: I-5 1,ID 1, Oregon 1 , PNW 1/2, PNWR 2 and/or WA 1&2.
So options are Yes/No/Partial for both MCT's and
Hold-off timers being coded into each manager. |
| Typical PTT talkgroups
have an "on-timer" for 15 minutes and most have
"hold-off timers" for 3 minutes. Not all
hold-off timers for the PTT TG's may be in place.
Some TG's have a bare minimum as indicated by "P15/0" as
they are quick to program and somewhat
useable for PTT purposes by repeaters that have not
expressly requested those particular talkgroups.
In other words, the talkgroup is programmed into the
manager and usable via PTT but the more involved
programming to implement the hundreds of hold-off timers, has
not been implemented. So it is probable
that other talkgroups may capture the slot and stomp
on these "zero" talkgroups, especially the full time
talkgroups. Somewhat of an approach that "it
is better than nothing". |
| Net 2 timers are PTT for 1 hour with Local 2 turning off
Net 2 for 1 hour. Some timeslot 2 FT
talkgroups will be held-off by Net 2 for
15 minutes |
Columns: F/y = Fulltime / Hold-off Timer (y min
or mct)
Columns: Px/y = PTT On Timer (x min) / Hold-off Timer (y min)
Columns: Pr/y = PTT On Timer (x min) r = Receive Only / Hold-off Timer (y min)
Columns: Px/0.f = HO's only for the fulltime
TG's for minimal control (.f = fulltime)
* =
talkgroup is PTT from Brandmeister |
Blank = No appearance of
TG on manager
Question Mark = unknown status, pending adoption
+ = Some hold-off timers are in place but incomplete programming
MCT controls = 55 or 59 min On / 15 or 29 min Off and may or may
not have supplemental HO's for fulltime talkgroups
for better experience |
n/a indicates
that a talkgroup may not be available to all
managers, in your area or may come with restrictions
on their use. These conditions are not
necessarily set by
PNW but may be part of an agreement with other
organizations which control their talkgroups
appearance, distribution and/or use. |
TAC's:
Are approved for many Washington repeaters but have
not yet been coded in every instance. Several
are complete and eventually all will be completed.
The Matrix is important for use of TAC's as much is
not yet coded. |
This
slate of talkgroups has been approved by each
repeater owner or manger admin. If you want
changes, additions or deletions, then the owner or
admin must agree to that. Please contact them
directly for discussion of any changes. |
Linked: By agreement; Local
1 for the CdA and Spokane repeaters are linked full time.
Local 1 and Local 2 are not connected outside of its
manager/IPSC network unless by special request.
Hold-off timers may turn off some networked
talkgroups for 5 minutes as a loose form of priority to locally
generated
traffic. Some custom managers may hold-off
talkgroups for up to 2 hours for Search and Rescue,
EMCOMM or other public
service events. |
This
matrix is now the baseline or controlling document to determine all
interactions on each manager. If you have any
issues with talkgroups, stomping on other
talkgroups, etc, please look to this chart,
determine what should be the listed action and then
armed with that information, report issues. |
LAST
THOUGHT: The coding of the c-Bridge bridge
groups and super groups is fairly complex soon
handling over 500 bridge groups and in excess of 50
talkgroups on 2 timeslots, but especially PNW's
timeslot 2 which has the bulk of the networked
talkgroups. There are around 7,500 programming
lines, each have up to 10 pieces of data (North
America alone had over 775 lines of coding at last
count). So, unless requested, not all
hold-offs on TS 2 have been created due to the
additional work/complexity and because the PTT TG's
have less potential to collide with the full-time
TG's. Coding mistakes in logic as well as typos,
inject more issues. So reporting problems is
encouraged to both excise the mistakes as well as
complete the hold-offs and MCT's as they are ever more
important as more talkgroups and managers are added
to the PNW c-Bridge. Your input is needed to reduce your users frustration soon TG activity
collides. If something occurs that you feel is
wrong, document and report it, ASAP so that the
logging info can be used to aid in fixes if it is
still available. |
